home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
rcs.z
/
rcs
Wrap
Text File
|
1998-10-20
|
15KB
|
331 lines
RRRRCCCCSSSS((((1111)))) RRRRCCCCSSSS((((1111))))
NNNNAAAAMMMMEEEE
rcs - change RCS file attributes
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
rrrrccccssss [ _o_p_t_i_o_n_s ] _f_i_l_e ...
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
rrrrccccssss creates new RCS files or changes attributes of existing ones. An RCS
file contains multiple revisions of text, an access list, a change log,
descriptive text, and some control attributes. For rrrrccccssss to work, the
caller's login name must be on the access list, except if the access list
is empty, the caller is the owner of the file or the superuser, or the ----iiii
option is present.
Pathnames matching an RCS suffix denote RCS files; all others denote
working files. Names are paired as explained in cccciiii(1). Revision numbers
use the syntax described in cccciiii(1).
OOOOPPPPTTTTIIIIOOOONNNNSSSS
----iiii Create and initialize a new RCS file, but do not deposit any
revision. If the RCS file has no path prefix, try to place it first
into the subdirectory ....////RRRRCCCCSSSS, and then into the current directory.
If the RCS file already exists, print an error message.
----aaaa_l_o_g_i_n_s
Append the login names appearing in the comma-separated list _l_o_g_i_n_s
to the access list of the RCS file.
----AAAA_o_l_d_f_i_l_e
Append the access list of _o_l_d_f_i_l_e to the access list of the RCS
file.
----eeee[_l_o_g_i_n_s]
Erase the login names appearing in the comma-separated list _l_o_g_i_n_s
from the access list of the RCS file. If _l_o_g_i_n_s is omitted, erase
the entire access list.
----bbbb[_r_e_v]
Set the default branch to _r_e_v. If _r_e_v is omitted, the default
branch is reset to the (dynamically) highest branch on the trunk.
----cccc_s_t_r_i_n_g
sets the comment leader to _s_t_r_i_n_g. An initial cccciiii, or an rrrrccccssss ----iiii
without ----cccc, guesses the comment leader from the suffix of the
working filename.
This option is obsolescent, since RCS normally uses the preceding
$$$$LLLLoooogggg$$$$ line's prefix when inserting log lines during checkout (see
ccccoooo(1)). However, older versions of RCS use the comment leader
instead of the $$$$LLLLoooogggg$$$$ line's prefix, so if you plan to access a file
with both old and new versions of RCS, make sure its comment leader
matches its $$$$LLLLoooogggg$$$$ line prefix.
PPPPaaaaggggeeee 1111
RRRRCCCCSSSS((((1111)))) RRRRCCCCSSSS((((1111))))
----kkkk_s_u_b_s_t
Set the default keyword substitution to _s_u_b_s_t. The effect of
keyword substitution is described in ccccoooo(1). Giving an explicit ----kkkk
option to ccccoooo, rrrrccccssssddddiiiiffffffff, and rrrrccccssssmmmmeeeerrrrggggeeee overrides this default. Beware
rrrrccccssss ----kkkkvvvv, because ----kkkkvvvv is incompatible with ccccoooo ----llll. Use rrrrccccssss ----kkkkkkkkvvvv to
restore the normal default keyword substitution.
----llll[_r_e_v]
Lock the revision with number _r_e_v. If a branch is given, lock the
latest revision on that branch. If _r_e_v is omitted, lock the latest
revision on the default branch. Locking prevents overlapping
changes. If someone else already holds the lock, the lock is broken
as with rrrrccccssss ----uuuu (see below).
----uuuu[_r_e_v]
Unlock the revision with number _r_e_v. If a branch is given, unlock
the latest revision on that branch. If _r_e_v is omitted, remove the
latest lock held by the caller. Normally, only the locker of a
revision may unlock it. Somebody else unlocking a revision breaks
the lock. This causes a mail message to be sent to the original
locker. The message contains a commentary solicited from the
breaker. The commentary is terminated by end-of-file or by a line
containing .... by itself.
----LLLL Set locking to _s_t_r_i_c_t. Strict locking means that the owner of an
RCS file is not exempt from locking for checkin. This option should
be used for files that are shared.
----UUUU Set locking to non-strict. Non-strict locking means that the owner
of a file need not lock a revision for checkin. This option should
_n_o_t be used for files that are shared. Whether default locking is
strict is determined by your system administrator, but it is
normally strict.
----mmmm_r_e_v::::_m_s_g
Replace revision _r_e_v's log message with _m_s_g.
----MMMM Do not send mail when breaking somebody else's lock. This option is
not meant for casual use; it is meant for programs that warn users
by other means, and invoke rrrrccccssss ----uuuu only as a low-level lock-breaking
operation.
----nnnn_n_a_m_e[::::[_r_e_v]]
Associate the symbolic name _n_a_m_e with the branch or revision _r_e_v.
Delete the symbolic name if both :::: and _r_e_v are omitted; otherwise,
print an error message if _n_a_m_e is already associated with another
number. If _r_e_v is symbolic, it is expanded before association. A
_r_e_v consisting of a branch number followed by a .... stands for the
current latest revision in the branch. A :::: with an empty _r_e_v stands
for the current latest revision on the default branch, normally the
trunk. For example, rrrrccccssss ----nnnn_n_a_m_e:::: RRRRCCCCSSSS////**** associates _n_a_m_e with the
current latest revision of all the named RCS files; this contrasts
PPPPaaaaggggeeee 2222
RRRRCCCCSSSS((((1111)))) RRRRCCCCSSSS((((1111))))
with rrrrccccssss ----nnnn_n_a_m_e::::$$$$ RRRRCCCCSSSS////**** which associates _n_a_m_e with the revision
numbers extracted from keyword strings in the corresponding working
files.
----NNNN_n_a_m_e[::::[_r_e_v]]
Act like ----nnnn, except override any previous assignment of _n_a_m_e.
----oooo_r_a_n_g_e
deletes ("outdates") the revisions given by _r_a_n_g_e. A range
consisting of a single revision number means that revision. A range
consisting of a branch number means the latest revision on that
branch. A range of the form _r_e_v_1::::_r_e_v_2 means revisions _r_e_v_1 to _r_e_v_2
on the same branch, ::::_r_e_v means from the beginning of the branch
containing _r_e_v up to and including _r_e_v, and _r_e_v:::: means from
revision _r_e_v to the end of the branch containing _r_e_v. None of the
outdated revisions may have branches or locks.
----qqqq Run quietly; do not print diagnostics.
----IIII Run interactively, even if the standard input is not a terminal.
----ssss_s_t_a_t_e[::::_r_e_v]
Set the state attribute of the revision _r_e_v to _s_t_a_t_e. If _r_e_v is a
branch number, assume the latest revision on that branch. If _r_e_v is
omitted, assume the latest revision on the default branch. Any
identifier is acceptable for _s_t_a_t_e. A useful set of states is EEEExxxxpppp
(for experimental), SSSSttttaaaabbbb (for stable), and RRRReeeellll (for released). By
default, cccciiii(1) sets the state of a revision to EEEExxxxpppp.
----tttt[_f_i_l_e]
Write descriptive text from the contents of the named _f_i_l_e into the
RCS file, deleting the existing text. The _f_i_l_e pathname may not
begin with ----. If _f_i_l_e is omitted, obtain the text from standard
input, terminated by end-of-file or by a line containing .... by
itself. Prompt for the text if interaction is possible; see ----IIII.
With ----iiii, descriptive text is obtained even if ----tttt is not given.
----tttt----_s_t_r_i_n_g
Write descriptive text from the _s_t_r_i_n_g into the RCS file, deleting
the existing text.
----TTTT Preserve the modification time on the RCS file unless a revision is
removed. This option can suppress extensive recompilation caused by
a mmmmaaaakkkkeeee(1) dependency of some copy of the working file on the RCS
file. Use this option with care; it can suppress recompilation even
when it is needed, i.e. when a change to the RCS file would mean a
change to keyword strings in the working file.
----VVVV Print RCS's version number.
PPPPaaaaggggeeee 3333
RRRRCCCCSSSS((((1111)))) RRRRCCCCSSSS((((1111))))
----VVVV_n Emulate RCS version _n. See ccccoooo(1) for details.
----xxxx_s_u_f_f_i_x_e_s
Use _s_u_f_f_i_x_e_s to characterize RCS files. See cccciiii(1) for details.
----zzzz_z_o_n_e
Use _z_o_n_e as the default time zone. This option has no effect; it is
present for compatibility with other RCS commands.
At least one explicit option must be given, to ensure compatibility with
future planned extensions to the rrrrccccssss command.
CCCCOOOOMMMMPPPPAAAATTTTIIIIBBBBIIIILLLLIIIITTTTYYYY
The ----bbbb_r_e_v option generates an RCS file that cannot be parsed by RCS
version 3 or earlier.
The ----kkkk_s_u_b_s_t options (except ----kkkkkkkkvvvv) generate an RCS file that cannot be
parsed by RCS version 4 or earlier.
Use rrrrccccssss ----VVVV_n to make an RCS file acceptable to RCS version _n by discarding
information that would confuse version _n.
RCS version 5.5 and earlier does not support the ----xxxx option, and requires
a ,,,,vvvv suffix on an RCS pathname.
FFFFIIIILLLLEEEESSSS
rrrrccccssss accesses files much as cccciiii(1) does, except that it uses the effective
user for all accesses, it does not write the working file or its
directory, and it does not even read the working file unless a revision
number of $$$$ is specified.
EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
RRRRCCCCSSSSIIIINNNNIIIITTTT
options prepended to the argument list, separated by spaces. See
cccciiii(1) for details.
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
The RCS pathname and the revisions outdated are written to the diagnostic
output. The exit status is zero if and only if all operations were
successful.
IIIIDDDDEEEENNNNTTTTIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN
Author: Walter F. Tichy.
Revision Number: 5.7; Release Date: 1998/01/12.
Copyright c 1982, 1988, 1989 by Walter F. Tichy.
Copyright c 1990, 1991, 1992, 1993, 1994, 1995 by Paul Eggert.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
co(1), ci(1), ident(1), rcsdiff(1), rcsintro(1), rcsmerge(1), rlog(1),
rcsfile(4), RCSsource(5)
Walter F. Tichy, RCS--A System for Version Control, _S_o_f_t_w_a_r_e--_P_r_a_c_t_i_c_e &
_E_x_p_e_r_i_e_n_c_e 11115555, 7 (July 1985), 637-654.
PPPPaaaaggggeeee 4444
RRRRCCCCSSSS((((1111)))) RRRRCCCCSSSS((((1111))))
BBBBUUUUGGGGSSSS
A catastrophe (e.g. a system crash) can cause RCS to leave behind a
semaphore file that causes later invocations of RCS to claim that the RCS
file is in use. To fix this, remove the semaphore file. A semaphore
file's name typically begins with ,,,, or ends with ____.
The separator for revision ranges in the ----oooo option used to be ---- instead
of ::::, but this leads to confusion when symbolic names contain ----. For
backwards compatibility rrrrccccssss ----oooo still supports the old ---- separator, but it
warns about this obsolete use.
Symbolic names need not refer to existing revisions or branches. For
example, the ----oooo option does not remove symbolic names for the outdated
revisions; you must use ----nnnn to remove the names.
PPPPaaaaggggeeee 5555